-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check for mallocx alignment behaviour. #19
Conversation
Locally, I still see a failure (due to the new |
For reference once we come back from the holidays, I've started another CI run to see how it goes [1]. |
Ok, 21b3c79 passes |
Please squash. |
This is, hopefully, a temporary measure to allow the run to complete before the Merge Queues timeout.
CTSRD-CHERI/cheribsd#1964 This was fixed, but the assertions here might be useful in case someone tries to run this on an affected CheriBSD.
This is mostly for symmetry with alignment (malloc), making it easier to verify that we're not breaking existing alignment constraints.
21b3c79
to
0cf8f85
Compare
Done, but the CI says "skipped" so I'm not sure if it worked or not. |
Ah, yes, "Skipped" is a bit weird :) We do that to "skip" the CI run that GitHub would like to run when a PR is raised/altered -- we only want to run CI when we press "merge". |
CheriBSD's revocation support is incompatible with
MALLOCX_ALIGN
andMALLOCX_ARENA
, so disable it in tests, and also add assertions toContinuousArenaMalloc
to ensure that we're actually getting aligned capabilities in the expected memory region.This PR also adds CapableVMs merge queues support.